Oracle Forms and Reports End of Life (EOL) Dates & Support Timeline

Oracle Forms and Reports lifecycle status — the real story

Oracle Forms and Reports' support windows come from Oracle's Fusion Middleware Lifetime Support Policy (edition effective April 13, 2026). From 12c on, Forms and Reports has no row of its own: Oracle lists it inside the Fusion Middleware 12c (12.2.x) and 14.1.x rows, so it shares the WebLogic and SOA Suite dates for each line. The 11gR1 and 11gR2 lines have their own rows, and 10gR2 (10.1.2.x) is covered by the Application Server 10gR2 row. Oracle publishes months only and states that "unless otherwise noted, each stage of support is provided through the last day of the month", so dates here are the last day of Oracle's month. "End of support" is the end of Premier Support and "extended support" is the end of paid Extended Support; Sustaining Support continues indefinitely but delivers no new fixes or security patches.

One exception matters for E-Business Suite customers: Oracle's Applications policy says customers running Fusion Middleware 10gR2 and 10gR3 in the E-Business Suite 12.1 internal technology stack "will remain supported for the duration of the support period for Oracle E-Business Suite 12.1", and that Fusion Middleware embedded in the E-Business Suite 12.2 technology stack stays supported for the duration of 12.2. A Forms 10.1.2 installation that is part of an EBS stack is therefore not covered by the 10gR2 dates on this page.

Oracle's Forms download page also lists error correction separately from lifetime support: for Forms and Reports 12.2.1.4.0 it says "Error correction support ended Sept 2024", and the current 12.2 build is 12.2.1.19.0. CISA's Known Exploited Vulnerabilities catalog files CVE-2012-3152 (Oracle Reports Developer, the Reports Server servlet) under the product name "Fusion Middleware"; it is attributed here by a reviewed override because the name does not token-match.

Oracle Forms and Reports release and support pattern

Of the 5 release lines tracked, 3 are past end of life and 2 are still within support. The next scheduled end of life is 12.2 on December 31, 2026 — 82 days from this build. The longest-supported line currently published is 14.1, to December 31, 2030. Upstream also publishes an extended-support phase for 4 lines, shown in the table above.

Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.

Oracle Forms and Reports security intelligence

CISA KEV history: Oracle Forms and Reports is named in CISA's Known Exploited Vulnerabilities catalog 1 time, most recently on 2021-11-03. Derived from CISA's live catalog at every build.

What does Oracle Forms and Reports end of life mean for your organization?

When a version of Oracle Forms and Reports reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.

The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.

Organizations running EOL Oracle Forms and Reports should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.

Your options when Oracle Forms and Reports reaches end of life

There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.

How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.

Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.

Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.

Extended Support Options

If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Oracle Forms and Reports versions. This is a bridge, not a permanent solution — plan your migration in parallel.

Related Products